Method and Apparatus For Monitoring Wireless Network Access

ABSTRACT

A system and method for monitoring wireless network access, and use of a detected wireless network connection are described. A client component (e.g., software component), or client, can be downloaded to a computing device, which leverages off of the computing device&#39;s ability to locate and establish a network connection. The client component listens for network connection activity, and determines whether the device has established a network connection with a network known to the client. If the client determines that a network connection has been established to a known network, the client uses the network connection to log the user onto the network.

CROSS REFERENCE To RELATED APPLICATION(S)

This application is a continuation of and claims priority to U.S.Utility patent application Ser. No. 11/769,268, entitled “Method andApparatus For Monitoring Wireless Network Access,” filed on Jun. 27,2007, which claims priority to U.S. Provisional Patent Application Ser.No. 60/833,529, entitled “Method and Apparatus For Monitoring WirelessNetwork Access,” filed on Jul. 25, 2006, the contents of both of whichare incorporated herein by reference in their entireties.

This application is related to U.S. patent application Ser. No.10/325,450, entitled “Method and Apparatus For Accessing Networks by aMobile Device,” filed on Dec. 19, 2002, the contents of which areincorporated herein by reference, and related to U.S. patent applicationSer. No. 11/435,019, entitled “Network Access Point Detection and Use,”filed on May 15, 2006, the contents of which are incorporated herein byreference.

A portion of the disclosure of this patent document contains materialwhich may be subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND OF THE INVENTION

1. Field of the Invention

A method and apparatus for monitoring wireless network access isdisclosed.

2. Background Discussion

Wireless networks have become more prevalent and provide a mechanism forconnecting to other networks, including the Internet. Wireless fidelity“WiFi” networks (e.g., 802.11 networks) have recently emerged as thedominant standard for wireless networks. This is largely due to the easewith which a WiFi network can be installed, and the minimal costinvolved. For example, an operator, can setup a “hot spot” with one ormore digital subscriber lines (DSLs) and/or T1 lines and equipment thatcontrols access to the wireless network, and then sell high speedwireless Internet access for a fee. A “hot spot” typically has one ormore wireless access points (APs) that serve as the connection pointbetween a customer's device and the WiFi network. The customer's devicecan be any device (e.g., desktop or laptop computer, personal digitalassistant, digital camera, mobile phone, automobile, gaming devices,consumer electronic equipment, etc.) which has a WiFi chip capable ofcommunicating with the wireless network.

As more and more hot spots are installed, there will be more of anopportunity for users to gain access to the Internet via a wirelessnetwork connection. Due to the number of different hot spot, or wirelessnetwork, operators and different mechanisms for gaining wireless networkaccess, however, wireless access to the Internet is not as seamless as auser would prefer it to be.

In order to gain access to a wireless network, a user must first haveauthorization from the wireless network operator, which typicallyrequires that the user have an agreement with the hot spot operator, oranother entity that has an agreement with the wireless network operator,which identifies the access terms and fees. Based on such an agreement,the wireless network operator provides the user with connection/loginprocedures, which the user must use to gain access to the operator'swireless network.

A user's WiFi-enabled device, or wireless device, typically has theability to sniff, or scan for, beacon frames, or signals, broadcast byaccess points which are a part of existing wireless networks. Moreparticularly, the wireless device will tune to one or more availablechannels and listen for all beacon frames, or signals, broadcast by thewireless networks on that channel. The beacons received by the devicecan be from one or more wireless networks, and one or more wirelessnetwork providers, each of which have different connection/loginprocedures.

The wireless device uses the beacon frames received to identify awireless network and corresponding wireless network provider.Thereafter, an attempt is made to connect to the wireless network usingthe appropriate login procedures for the network provider. Obtaining andmaintaining access to a wireless network is not simple due in large partto the number of wireless networks, and corresponding network providers,available and the fact that the user is “mobile” and attempting to enjoya seamless network access despite being mobile. A typical wirelessdevice periodically receives beacon frames broadcast by various accesspoints, which can be used to change to a different access point and/orwireless network. The latter change might require the wireless device toestablish a connection with a different wireless network and differentwireless network connection procedures than that used with a previousconnection. To be truly mobile, the user's device might need to interactwith multiple wireless networks and wireless network providers, and thediverse connection (e.g., login) procedures required by each of thewireless network providers.

SUMMARY

In accordance with one or more embodiments, a utility is provided tofacilitate a user's wireless network access, such that interaction withvarious connection procedures required by different wireless networkproviders is transparent to the user. Such a utility can take advantageof capabilities of modern operating systems' ability to establish alow-level connection (e.g., layer 2 connectivity) to a wireless network,by detecting such a low-level connection and establishing a high-levelconnection, which can be used by the user to access the wirelessnetwork. In addition, such a utility can be used in connection withaspects described in U.S. patent application Ser. No. 10/325,450,entitled “Method and Apparatus For Accessing Networks by a MobileDevice”, and U.S. patent application Ser. No. 11/435,019, entitled“Network Access Point Detection and Use” to be able to determine whetherthe low-level connection can be used to establish a wireless networkconnection. Furthermore and in a case that multiple wireless networksfrom different network providers are available, a utility is provided toselect a preferred provider, either automatically or by alerting theuser and allowing the user to make the selection.

In accordance with one or more embodiments, a client utility, alsoreferred to herein as a client, need not scan for, or associate to, anetwork. In accordance with such an embodiment, the client detects thata low-level network connection has been established, and performs anautomated login process for the user. A type of detection used by such aclient is passive in that it does not perform active scanning for awireless network (e.g., detecting beacon frames broadcast by wirelessnetworks). Rather, the client is installed on a client device and allowscapabilities provided by the client device's operating system to performthe active scanning

In accordance with embodiments disclosed herein, the client can beinstalled on a client device as a part of the user's signup process witha network provider. In accordance with disclosed embodiment,installation of the client can include an automatic configuration of theclient to include the user's username and password, which can be used toconnect to a wireless network, thereby avoiding the need for the user toprovide this information (e.g., at a time when the client is installedand/or connection to a wireless network is attempted).

In accordance with one or more embodiments, a client component (e.g.,software component), or client, can be downloaded to a computing device,which leverages off of the computing device's ability to locate andestablish a network connection. The client component listens for networkconnection activity, and determines whether the device has established anetwork connection with a network known to the client. If the clientdetermines that a network connection has been established to a knownnetwork, the client uses the network connection to log the user onto thenetwork.

Advantages of this approach include a client that can have a lighterfootprint (size, resource needs, etc.) than might otherwise be needed,since the client can rely on other components to perform establish aconnection with a network. In addition, the client can rely on devicecomponents to establish the network connection, but the client cancontrol (or at least direct) the manner in which the user is logged ontothe network. For example, the client can prompt the user to choose aparticular account to log onto the network, rather than another account,if the client determines that the network connection is such that theuser can use the first account. The client can then either select theaccount for the user, or prompt the user to select the account, in acase that the account is available to the user.

Other aspects include a download process used to download the clientsoftware component as well as configuration information, including userauthentication information, as a downloadable file. Advantageously, thedownload process integrates the steps of transferring the clientcomponent to the computing device, installing the client on thecomputing device, and configuring the client to use the user'sauthentication information. This process is more automatic and moreconvenient to the user than multiple discrete manual steps. The processcan be used, for example, to eliminate a need for the user to manuallystart an installation process or to re-input the user's authenticationinformation (e.g., at a time when the user is attempting to log onto thewireless network).

DRAWINGS

The above-mentioned features and objects of the present disclosure willbecome more apparent with reference to the following description takenin conjunction with the accompanying drawings wherein like referencenumerals denote like elements and in which:

FIG. 1, which comprises FIGS. 1A and 1B, provides an architecturaloverview example of components used in accordance with one or moreembodiments of the present disclosure.

FIG. 2, which comprises FIGS. 2A, 2B and 2C, provides an example of aclient process flow in accordance with one or more embodiments of thepresent disclosure.

FIG. 3, which comprises FIGS. 3A, 3B and 3C, provides a detailed clientprocess flow for use in accordance one or more embodiments of thepresent disclosure.

FIG. 4, which comprises FIGS. 4A to 4F, provides examples of dialogspresented to a user during a sign up process for use with one or moreembodiments disclosed herein.

FIG. 5, which comprises FIGS. 5A to 5G, provides examples of userinterface widgets which provide feedback to a user during a networklogon process in accordance with disclosed embodiments.

DETAILED DESCRIPTION

In general, the present disclosure includes a network access pointdetection and use system and method.

Certain embodiments of the present disclosure will now be discussed withreference to the aforementioned figures, wherein like reference numeralsrefer to like components. Although embodiments of the present disclosureare described with reference to the 802.11 wireless network environment,it should be apparent that the disclosed embodiments have application toother network environments, including other wireless networkingenvironments, examples of which include, without limitation, IEEEStandards 802.15, 802.16 and 802.20, Wireless Local Area Networks(Wireless LANs), Wireless Personal Area Networks (Wireless PANs), andWireless Metropolitan Area Networks (Wireless MANs), etc.

In accordance with one or more disclosed embodiments, client software,or client, executing on a user's client device, or device, is used todetect a low-level wireless network connection and to use the low-levelnetwork connection to connect the user to a wireless network. The clientcan be downloaded as part of a process in which a user signs up with agiven wireless network provider. For example, during the sign upprocess, the user provides certain information about the user (e.g.,name, address, payment details such as credit card information, andauthentication information such as username and password). As part ofthe sign up process, the user can be presented with a choice ofdownloading the client. If the user elects to download the client, theprogram code for the client is downloaded to the user's device, togetherwith the authentication information needed to authenticate the user toconnect to a wireless network.

FIG. 1, which comprises FIGS. 1A and 1B, provides an architecturaloverview example of components used in accordance with one or moreembodiments of the present disclosure. Device 108 is a wireless-enableddevice. A wireless-enabled device can be any device that includesnetwork interface function, which can be provided by an operating systemor some other software, e.g., software provided by a wireless networkprovider or WiFi chip hardware manufacturer, for example. Examples ofsuch a device include, but are not limited to, desktop or laptopcomputer, personal digital assistant, digital camera, mobile phone,automobile, gaming device, consumer electronic equipment, and the like.

In accordance with one or more embodiments, device, 108 comprises one ormore network drivers (or interfaces) 152, operating system (or O/S) 158,AP database 168 and client 167. Each network driver 152, which can be adriver such as an operating system-level driver for example, can be usedto connect to an AP 112 instance of a wireless network 102, and then tosend and receive network transmissions. In accordance with embodimentsof the present disclosure, client 167 is configured to detect a networkinterface connection using information provided by O/S 158, identify anappropriate network connection (and AP 112) using AP database 168, andlog into a wireless network using account information for the userretrieved form AP database 168. In accordance with embodiments disclosedherein and in the patent applications reference herein, AP database 168can contain a list of SSIDs and references to login scripts, e.g., foruse in logging onto a wireless network. AP database 168 can be storedlocally on device 108, and can be updated on a periodic basis. U.S.patent application Ser. No. 10/325,450, which is incorporated herein byreference, provides examples of its contents and mechanisms for updatingand maintaining AP database 168. In accordance with one or moreembodiments presently disclosed, AP database 168 can include all or someportion of the information identified in U.S. patent application Ser.No. 10/325,450. For example and in accordance with one or moreembodiments disclosed herein, an AP database 168 entry comprises an SSIDand corresponding script information.

The example architecture shown in FIG. 1A includes instances of wirelessnetwork 102. Each instance of wireless network 102 can include one ormore instances of access point (AP) 112. AP 112 is a networking devicethat serves as a communication or connection point for a device 108 andwireless network 102. Using wireless network 102, device 108 can gainaccess to the Internet 106, wired network 104, and/or other instances ofwireless network 102, for example.

A wireless network 102 instance can include, but need not include, oneor more instances of access controller 114. Access controller 114comprises a device used to control access to wireless network 102.Access controller 114 can be used to enforce a wireless networkoperator's rules for accessing wireless network 102, and/or Internet106. Access control can be accomplished by, for example, allowing anetwork component of device 108 to associate with network 102 withoutrequiring authentication, and then blocking the device's 108 trafficuntil valid authentication information is provided. Access controller114 is typically used with commercial instances of wireless network 102,such as one provided by a hot spot operator. Another instance ofwireless network 102, such as one used in a home environment, need notinclude an access controller 114. Each instance of wireless network 102can have specific procedures, or methodologies, for associating,authenticating, and/or connecting to the network, which can (and likelydo) vary from one instance to another of wireless network 102.

One example of a scenario that might be used involves a process ofreceiving the device's 108 initial Web page request, and redirecting therequest to access controller 114, which requests the authenticationinformation from the device 108. If the device 108 provides validauthentication information, access controller 114 permits unrestricteduse of wireless network 102 by the device 108.

In accordance with one or more embodiments presently disclosed, client167 can detect such an association and then provide the requiredauthentication so as to establish a network connection, or session, fora user of device 108.

In accordance with at least one embodiment, server 130 can be used todownload client 167. In addition, server 130 can be used to transmitother data, including configuration information for client 167,incremental updates to such configuration information, and/or updates toclient 167.

In the example architecture shown in FIG. 1A, a single device 108 andserver 130 are shown for the sake of simplicity. It should be apparentthat there can be multiple instances of device 108 and/or multipleinstances of server 130.

FIG. 1B provides an example of an internal architecture of device 108 inaccordance with one or more embodiments of the present disclosure. Itshould be apparent that device 108 can include additional components.Such additional components can, for example, depend on the type ofdevice. Device 108 comprises a central processing unit (CPU) 151, one ormore instances of network driver 152, one or more instances ofInput/Output (I/O) device interface 153, and memory 154, all of whichcan interface via bus 150. Network driver 152 can comprise a wirelessnetwork driver, which can control a WiFi circuitry, for example. Atleast one instance of network driver 152 has the capability to detectinstances of AP 112, and to send and receive network communicationsusing a network communications protocol such as that defined by theTransmission Control Protocol/Internet Protocol, or TCP/IP, protocolsuite. Memory 154 can comprise a combination of temporary and persistentstorage, and can include random access memory (RAM). Contents of memory154 comprise cache 155, configuration 156, client 167, operatingsoftware platform 158, and AP database 168. In addition, memory 154 caninclude permanent storage in addition to RAM. Examples of suchpersistent storage include, but are not limited to, flash memory anddisk storage (e.g., fixed or removable), CD, etc.

O/S 158 includes program code executable by CPU 151 to control theoperations of device 108. In accordance with one or more embodiments,O/S 158 includes a facility to allow client 167 to monitor activity ofnetwork driver 152, so as to identify an appropriate network connection,for example. Examples of configuration 156 include, without limitation,parameters used to control client 167, updates to AP database 168, loginprocedures and/or scripts, etc.

Referring again to FIG. 1A, AP 112 instances broadcast beacon frames119. Network driver 152 “scans” 120, also referred to herein as “sniffs”or detects, a beacon frame 119 broadcast by an instance of AP 112. Thatis, for example, network driver 152 of device 108 listens for beaconframes 119 broadcast on a given channel by instances of AP 112. A beaconframe 119 typically includes information such as an SSID, BSSID, as wellas security settings. Network driver 152 is further configured totransmit a connection request 123 and to receive a connection response124, and to transmit and receive network transmissions.

FIG. 2A provides an example of a client process flow in accordance withone or more embodiments of the present disclosure. Generally and inaccordance with one or more embodiments, once installed on a clientdevice, the client 167 executes in the background to detect a networkinterface connection, determine whether the network interface connectioncan be used to log the user into a wireless network. In accordance withone or more embodiments, the client 167 can start automatically and runin the background on device 108 at the end of the signup process, so asto be invisible to the user. The client 167 can remain in this stateuntil a network interface connection to a hot spot is made by aninstance of network interface 152.

In addition and in accordance with one or more embodiments, the client167 can start automatically after it is installed on a device 108. Theclient 167 can also be invoked whenever the device 108 is restarted aspart of loading the operating system (“O/S”), for example.

At step 201, upon startup and until the client 167 exits, the client 167operates to detect a network interface connection and to use a detectednetwork interface connection to log onto a wireless network 102. Inaccordance with one or more embodiments, there is no user interfacevisible for client 167 during startup/initialization of client 167, orwhile the client 167 operates to detect a network interface connection.In accordance with one or more embodiments, client 167 can receiveevent/state information via notifications/messages from O/S 158. Atstartup, in accordance with one or more embodiments, the client 167 canimplicitly generate a message for its own consumption reflecting theconnected state of a given interface.

At step 202, the client 167 listens for events generated by one or moreinstances of network driver 152 via O/S 158. In accordance with one ormore embodiments, the client 167 can register with O/S 158 to receiveevents associated with network driver 152. Such events can signal achange in a state of a network interface connection, for example. Whenmessages related to the interface are received from the O/S 158, theclient 167 can check the content of these messages to see whether asuccessful network interface connection has been established. A networkinterface connection can be considered to be established based on anumber of criteria, such as the physical or logical connection to anetwork, or the assignment of an Internet Protocol (IP) address by thenetwork to the computer on which the client is running, for example.

For each network interface connection event, or state change, the client167 determines whether the detected event signals that a network driver152 has established a network interface connection with an AP 112instance, at step 203. When client 167 determines that a networkinterface connection is established on a relevant interface (e.g., via anetwork driver 152 instance), the client 167 determines a network namecorresponding to the network interface connection. For example, in acase of a Wi-Fi network, a network name can be provided by the ServiceSet Identifier, or SSID, as defined in the 802.11 standard. On othernetworks, a different identifier may be used.

In accordance with one or more embodiments, the client 167 accesses, andmaintains, a database of known SSIDs, AP database 168. If the SSIDcorresponding to the network interface connection identified by theclient 167 matches a known SSID (e.g., corresponds to an entry in thedatabase maintained by the client), the client 167 can initiate a loginprocess to log the user into the wireless network via the detectednetwork interface connection. Thus, at step 204, client 167 queries APdatabase 168 to identify the wireless network 102 associated with the AP112 instance, and whether there is a logon procedure available for theidentified wireless network 102 to connect the user. In addition and atstep 204, a determination is made whether or not the user is currentlylogged on and/or whether a new connection should be established for theuser. If a new/replacement connection is to be made and the AP 112instance can be used to establish the connection, processing continuesat step 205 to perform the login process. As is discussed herein, in acase that there are multiple login procedures (e.g., for multipledifferent providers) available, the user can be prompted to select oneof the login procedures/providers.

In accordance with one or more embodiments, once the client exits atstep 201, the client 167 will stop listening for notifications/messagesfrom O/S 158 related to network interface changes at step 206.

As such, the client 167 need not conduct an active scan for broadcastbeacons to identify an available network in order to make a networkconnection for the user. Instead, the client 167 can rely on the O/S 158or other software on the user's device 108 to locate a suitable AP 112of a wireless network 102. Once a suitable AP 112 is identified, client167 can be configured as is described in U.S. patent application Ser.No. 10/325,450 and/or U.S. patent application Ser. No. 11/435,019, thecontents of both of which are incorporated herein, to interact with thegateway (e.g., AP 112 and access controller 114) using a scriptingmechanism and configuration information, for example, as describedtherein.

Advantageously, embodiments of the present disclosure recognize thatmany users initiate a network connection by opening a web browserwindow, which action results in O/S 158 and network driver 152responding and establishing a network interface connection. Inaccordance with embodiments disclosed herein, the client 167 can takeadvantage of this capability provided by the O/S 158 and network driver152, and need not include such functionality. Once an appropriatenetwork interface connection is located, the client 167 can use thedetected network interface connection to log the user into a wirelessnetwork 102.

The login procedure used by the client can depend on the wirelessnetwork provider on a predetermined configuration or based on aselection made by the user in an interaction between the user and a userinterface caused to be displayed by client 167 as part of a logonprocedure. In accordance with embodiments disclosed herein, client 167can utilize functionality external to the client 167 (e.g.,functionality provided by O/S 158) to establish a network interfaceconnection, but still retain control of the logon process and/orinteract with the user during the logon process. As is discussed herein,the client 167 can interact with the user to offer alternatives to theuser, such as which wireless network account/provider to use to connectto a wireless network 102.

In accordance with one or more embodiments, the client 167 canalternatively perform probing in certain circumstances, as will bedescribed with reference to the client process flow illustrated in FIG.2B. The client process flow associated with probing illustrated in FIG.2B is performed between steps 204 and 205 of FIG. 2A. After step 204,the client 167 determines whether the network 102 requires probing instep 210. In some embodiments, the client 167 could determine thatprobing is required from a field in the AP database 168. If the network102 does not require probing, the client process flow would continue onto the login process in step 205 as described previously with referenceto FIG. 2A.

If the network 102 does require probing, the client 167 will determinewhether there exists a reliable cache or history of probing data in step211. In accordance with embodiments disclosed herein, the cache wouldstore the BSSIDs of networks that have been previously probedsuccessfully and, additionally, could also store the BSSIDs for networksthat have failed previous probes. If a probe result was found in the APdatabase 168 by the client 167, the client process flow would continuewithout further probing. If no probe result was found for the network,the client 167 would perform a probe for the network in step 212.

A probe determines whether the client 167 would be able to login to thenetwork 102 by interacting with the access gateway. One example of aprobe would be inspecting the contents of the webpage served up by thegateway and determining whether it contains certain identifiableparameters, such as a location idea parameter. Another example of aprobe would be performing a mock login procedure against the gatewayand, in the situation where pre-defined login responses are detected,concluding that a network is usable. In some embodiments describedherein, probing is performed dynamically based on configuration data,such as is performed in the login portion of client process flowdescribed herein or described in U.S. patent application Ser. No.10/325,450 and/or U.S. patent application Ser. No. 11/435,019. Oneexample of probing described in such applications involves: detecting abeacon message from at least one access point of the wireless network,the beacon message including information identifying the access point;attempting, using at least one predefined operation, to communicate withthe access point; determining a usability status based on a responsereceived from the access point to the at least one predefined operation;and storing the determined usability status in a cache, the usabilitystatus being associated with a unique identifier of the access point.The foregoing probing examples are merely presented for illustrativepurposes and are not intended to encompass all possible manners ofperforming the probe. The probing results are then stored in cache.

Next, the probe result, either the current from step 212 or a cached oneidentified from step 211 related to the connected AP, is evaluated instep 213. If the probe failed, there will be no attempt to login and theclient process flow will return to step 201. If the probe is successfulsuccess, the client 167 will attempt to perform the login process instep 205 as previously described in connection with FIG. 2A.

In one or more embodiments described herein, the probing capabilitymakes it possible for the client 167 to work correctly on networks thatuse one SSID to cover more than one behavior model. For example, a largescale network may have a plurality of sub-networks (e.g., an airportnetwork, a hotel network, a coffee shop network, etc.) that all use thesame SSID, but depending on particular contract, companies may only beentitled to use certain ones of the sub-networks. The probing makes itpossible for the client 167 to recognize the large scale network andthen determine, based on configuration, which of the sub-networks isidentified and only try to login to locations where it knows it willhave a chance of success (i.e., an authorized sub-network).

In accordance with one or more embodiments, the client 167 can furtherinclude a signup process, as will be described with reference to theclient process flow illustrated in FIG. 2C. The client process flowassociated with the signup process illustrated in FIG. 2C is performedbetween steps 204 and 205 of FIG. 2A. After step 204, the client 167determines whether the user has signed up or subscribed for service andhas already provisioned their client 167 in step 220. If the user isalready subscribed, the client process flow continues to step 205 toperform the login process as described in connection with FIG. 2A. Ifthe user has not yet signed up for service, the client 167 determines instep 221 whether the user has already been given an opportunity to signup this connection attempt. If such an opportunity has been provided tothe user, the user will not again be offered the opportunity to sign upuntil the next time the user connects to the network and the clientprocess flow will return to step 201. In one embodiment, the client 167may provide the user with an option of not being asked again aboutsignup.

If the user has not yet been provided with an opportunity to signup forservice, the client 167 determines in step 222 whether the networkallows for a connection to the signup server. Some networks will allow auser to signup for service while others will not, thus the determinationof step 222 will prevent a user from being prompted to sign up forservice when the client 167 cannot connect to the server to complete thesignup process. If the network does not allow connection to the signupserver, then the client process flow will return to step 201. If thesignup server can be reached, the user is provided with the opportunityto signup in step 223. In one or more embodiments, an interface isprovided that allows the user to signup for an account. At theconclusion of signup, if the user has successfully completed the signupprocess, the client 167 is provisioned with the new signup information(e.g., username and password) provided to the user. In one or moreembodiments, this information is communicated between the signup serverand the client without the user having to provide such information.Alternatively, the user can be prompted to provide such information. Instep 224, the client determines whether the signup has been completed.If the signup process was not completed, the client process flow willreturn to step 201. If signup was completed, the client process flowwill continue to the login step 205 as described previously.

FIG. 3, which comprises FIGS. 3A and 3B, provide a detailed clientprocess flow for use in accordance one or more embodiments of thepresent disclosure.

At step 301, which can be performed by client 167 at startup, client 167identifies and enumerates the network components (e.g., network drivers152) present on device 108. In a case of Microsoft Windows, client 167can examine network drivers 152 visible through the Windows standardNetwork Driver Interface Specification (NDIS) system.

For each candidate driver 152 found, the client 167 determines whetherthe network component is of interest to client 167. In a case of aWindows system, this can be done by looking at NDIS Object Identifiers(OIDs) corresponding to the network component found at step 301, inorder to determine whether an OID corresponds to a Wi-Fi interface,e.g., those OIDs that describe 802.11 properties of an interface, suchas OID_(—)8021_(—)11 OIDs, and in particularOID_(—)802_(—)11_NETWORK_TYPE and OID_(—)802_(—)11_SSID. This process isperformed by steps 302 to 305, which examine each of the networkcomponents identified in step 301, to find “wireless network componentsand create a list of applicable network components, e.g., networkdrivers 152.

Client 167 monitors the identified network components, instances ofnetwork driver 152, to determine whether or not a connection stateassociated with any of the identified network components changes, e.g.,to detect whether a state of a network interface connection changes. Forexample and in a case of Microsoft Windows, client 167 can examine NDISOIDs signaling connection state changes on the interfaces, at step 306.In a case of Windows, for example, this can be done by monitoring NDISOIDs for layer 2 connectivity.

To further illustrate by way of an example if O/S 158 comprises aMicrosoft Windows O/S, client 167 can monitor NDIS OIDs to identifyconnection status changes at the MAC layer, and identify IP Addresschanges. In a case that client 167 detects an IP Address change, client167 can look for a network identifier in the NDIS OID information forthe given network driver 152 to retrieve an SSID. In a case that theSSID corresponding to a known network (e.g., the SSID exists in the APdatabase 168), client 167 can attempt to log the user onto the wirelessnetwork 102, using any one of a number of login procedures, includingthose described in U.S. patent application Ser. No. 10/325,450 and/orU.S. patent application Ser. No. 11/435,019.

If client 167 determines, at step 307, that there is a change in anapplicable network interface connection, processing continues at step309 to determine whether the change reflects a establishment of a layer2 network connection, e.g., a network driver 152 has connected to anetwork at a low level and is able to perform basic networkconnectivity. If such a change in status is detected, processingcontinues at step 310 to determine whether the network with which aconnection has been made is a known network. For example, client 167 canquery AP database 168 using the SSID associated with AP 112 to which thenetwork driver 152 is in communication to determine whether the SSID isa known SSID. In the case of an 802.11 network, this is done by checkingthe Service Set Identifier (SSID) of the network; in other networksanother unique identifier may be used. On Windows, the SSID can beretrieved by examining an NDIS OIDs that contains the 802.11 networkname, e.g., OID_(—)802_(—)11_SSID. If the network is known (e.g., thenetwork is a known commercial network), processing continues at client167 to identify the known network for monitoring, e.g., to determinewhether or not a layer 3 connection is established. Thereafter, and ifthe network is determined not to be known (i.e., client 167 need notmonitor a connection to an unknown network), processing continues atstep 306 to monitor the network interface components.

If a known network is identified at step 311, the client 167 monitorsthe networking subsystem of O/S 158 to determine whether a layer 3 IPconnection becomes available on the relevant network driver 152, at step312. If a layer 3 connection is detected at step 312, processingcontinues at step 313 to log onto the wireless network 102 using theuser's authentication information, e.g., authentication informationprovided by the user at the time that client 167 was transferred todevice 108. In accordance with one or more embodiments, client 167 caneither prompt the user with a dialog containing their username andpassword, allowing the user to click a Login button to start the loginprocess, or client 167 can automatically start the login process, e.g.,without user interaction. In accordance with one or more embodiments, anicon can be presented in a status area of a user interface displayableby device 108 to indicate that a connection is active and a login isrequired (e.g., the icon shown in FIG. 5B).

In accordance with one or more disclosed embodiments, client 167simultaneously monitors for changes in a network interface component,and for changes in a network connection in which the user is logged intoa wireless network 102. In a case of Windows, for example, a standardWindows Messaging Interface subsystem can be used to monitor IP changeson the interface (e.g., the connection on which the user is connected towireless network 102), while at the same time continuously checking theapplicable interfaces to identify whether there are any functional IPaddresses (e.g., a layer 2 or layer 3 connection).

In accordance with one or more embodiments, the client 167 canalternatively perform probing in certain circumstances, as will bedescribed with reference to the client process flow illustrated in FIG.3C that is performed between steps 312 and 313 of FIG. 3B. After step312, the client 167 determines whether the network 102 requires probingin step 312. In some embodiments, the client 167 could determine thatprobing is required from a field in the AP database 168. If the network102 does not require probing, the client process flow would continue onto the login process in step 313 as described herein with reference toFIG. 3B.

If the network 102 does require probing, the client 167 will determinewhether there exists a reliable cache or history or probing data in step321. In accordance with embodiments disclosed herein, the cache wouldstore the BSSIDs of networks that have been previously probedsuccessfully and, additionally, could also store the BSSIDs for networksthat have failed previous probes. If a probe result was found in the APdatabase 168 by the client 167, the client process flow would continuewithout further probing. If no probe result was found for the network,the client 167 would perform a probe for the network in step 322, suchas but not limited to the probing techniques described above inreference to step 212 of FIG. 2B.

Next, the probe result, either the current from step 322 or a cached oneidentified from step 321 related to the connected AP, is evaluated instep 323. If the probe failed, there will be no attempt to login and theclient process flow will return to step 302. If the probe is successfulsuccess, the client 167 will attempt to perform the login process instep 313.

Referring again to step 313 of FIG. 3B, in accordance with one or moreembodiments, client 167 retrieves a login script associated with theSSID of the AP 112 instance identified by client 167 from the store ofscripts (e.g., the script store provided by AP database 168), andexecutes the script. By way of non-limiting example, use of a script ina log in process is described in U.S. patent application Ser. No.10/325,450. In accordance with one or more embodiments, if the loginsucceeds, an appearance of an icon, such as that shown in FIG. 5B can bechanged to reflect that the user was successfully logged onto thenetwork. For example, the appearance of the icon shown in FIG. 5B can bealtered as shown in FIG. 5E, when the user is successfully logged ontothe network. In addition or alternatively, in accordance withembodiments, a dialog can be presented to the user to indicatesuccessful network login. For example, FIG. 5D provides an example of adialog that can be presented to the user to notify the user that thelogon procedure was successful. In accordance with one or moreembodiments, a dialog can be presented to the user can be presented tothe user during the logon process, an example of which is shown in FIG.5C.

In accordance with one or more embodiments, the icon shown in FIGS. 5Band 5E can be used by the user to display the window shown in FIG. 5D,to allow the user to log off of the network. In such a case, anyapplicable script, e.g., a logout script stored in AP database 168corresponding to the network, can be used to control client 167 tologout of the network. Use of a script to control client 167 to log ontoor off of a network is discussed in more detail in U.S. patentapplication Ser. No. 10/325,450 and/or U.S. patent application Ser. No.11/435,019, the contents of both of which are incorporated herein byreference.

In a case that the login procedure fails, a dialog, e.g., the dialogshown in FIG. 5F, can be displayed to the user, which allows the user toattempt another login. In a case that the login procedure fails, anotherdialog can be presented, which contains relevant technical informationhelpful in troubleshooting, such as the dialog shown in FIG. 5G. FIG. 5Gcan be displayed in response to the user selecting the “See SupportPage” link provided in the dialog shown in FIG. 5F. The dialog shown inFIG. 5G can be used to display information regarding the network theuser is connecting to and the client software in use. For example and asshown in the example of FIG. 5G, the information can include softwareversion information, database version information, network SSID, networkaddresses on both the IP and MAC layer, and an identifier of the scriptused in attempting to connect the user to the network, as well as asupport contact number.

Once a user is logged in, the client 167 can continue to monitor theapplicable interfaces. If a disconnect is detected on a networkinterface connection at step 314, the client 167 can notify the user ofa change in the connection status at step 315. For example, client 167can cause the icon shown in FIG. 5E to change in appearance, e.g., theicon's appearance changes to that shown in FIG. 5B. For example, anappearance of the icon can change by changing the color of a portion ofthe icon. It should be apparent that any type of notification can beused with embodiments presently disclosed. Processing continues at step306 to monitor the applicable interfaces.

In accordance with one or more embodiments, client 167 can be used toprompt the user to select an account associated with a certain wirelessprovider, in a case that multiple wireless providers might be available,for example. FIG. 5A provides an example of a dialog used to alert theuser that a given wireless provider account is available for use inaccordance with embodiments of the present disclosure. In accordancewith at least one embodiment, such a dialog window is displayed on ascreen of device 108, and sits on top of other application windows. Inaccordance with one or more embodiments, the given wireless networkprovider identified by client 167 corresponds to the wireless networkprovider from which client 167 was provided during a sign up process. Inaccordance with one or more embodiments, the network provider comprisesan aggregate network provider which acts to aggregate multiple networkproviders to the user, such that the aggregate network provider providesan interface between the user and the multiple network providers. Theusername and password provided by the user as part of the signup processcan be used to “pre-populate” the login window. Thus, the user cansimply select the “Login” button in order to start the authenticationprocess, to log onto a hot spot.

In accordance with one or more embodiments, client 167 can use a networkconnection, to automatically check for updates to its configuration 166,which can include updates to AP database 168, scripts referenced by APdatabase 168, and/or software updates, for example. A process to updatesuch information is further described in U.S. patent application Ser.No. 10/325,450, for example.

FIG. 4, which comprises FIGS. 4A to 4F, provides examples of dialogspresented to a user during a sign up process for use with one or moreembodiments disclosed herein.

FIGS. 4A and 4B provide examples of a window displaying sign-up forms.FIG. 4A can be displayed after the user has picked a usage plan of thewireless provider and provided personal information (e.g., full name,address, etc.), to allow the user to select a username and password. Asdiscussed, this input can be saved and used to automatically configureclient 167 on device 108 such that the user need not re-enter thisinformation.

FIG. 4B can be used to display a confirmation dialog, which includes acheckbox to allow the user to confirm the download of the program codein which functionality of client 167 software is embodied, and toconfirm corresponding terms and conditions. In accordance with one ormore embodiments, by default, the checkbox is selected, which can causean automatic download of the software when the user presses the “Submit”button on the form. If the user does not wish to download the software,the user can remove the check in the checkbox (e.g., “un-check” thecheckbox).

In accordance with one or more embodiments, when the file containing theprogram code is downloaded, the username and password provided by theuser can be are included as part of the file's filename downloaded tothe device 108. A simple encoding scheme can be used, resulting in aunique filename for each user that signs up. FIG. 4C provides an exampleof a download dialog which includes a filename comprising an encodedusername and password. Subsequently, a dialog can be displayed by O/S158, such as that shown in FIG. 4D, which prompts the user to executeprogram code contained in the file downloaded to device 108.

When the user selects the “Run”, the installation process can be invokedby O/S 158, and a dialog such as that shown in FIG. 4E can be displayed.Since authentication information, e.g., username and password, wereprovided as part of the information downloaded to device 108, the userneed not provide any input during the setup process, i.e. the user neednot provide a username, password or any other installation information.Client 167 is installed and automatically configured with a username andpassword, e.g., the same one the user provided during the signupprocess. In accordance with one or more embodiments, downloading of aclient 167 onto the user's device, and the provisioning of the clientwith the user's authentication information is integrated with the user'ssigning up for Wi-Fi service.

In accordance with one or more embodiments, client 167 need not beinvolved in the initial stages of Wi-Fi connectivity on a device 108,and can become involved at a time that a viable/usable networkconnection is detected. In addition and in accordance with one or moreembodiments, an installation process, which includes an installation ofclient 167, can be performed as part of user signup process. Usernameand password information, or any other authentication information,supplied by the user during the signup process is downloaded to device108, such that the user need not manually enter a username and passwordin order to log onto a wireless network using the account correspondingto the authentication information. An installed client 167 can assumethat another mechanism available on device 108, such as O/S 158 and/ornetwork drivers 152 (which can be a part of O/S 158), can be used toprovide core functionality to connect to the Wi-Fi Network.

Thus, embodiments disclosed in U.S. patent application Ser. Nos.10/325,450 and 11/435,019 can be modified such that a client component,e.g., access client 100 of device 102 described in U.S. patentapplication Ser. No. 10/325,450 and a configured client 108 described inU.S. patent application Ser. No. 11/435,019, can make use offunctionality internal to an operating system (e.g., O/S 158) or othersoftware or program code, which can establish a network connection at alevel that the client component can log a user onto wireless network102, and establish a session for the user.

With reference to U.S. patent application Ser. No. 10/325,450, forexample, client 167 can be used to augment, supplement or to modify,functionality provided by access client 100, such that access client 100need not detect carrier network signals. Rather, access client 100 canmonitor network driver 152 and/or O/S 158 network detection andassociation activity (e.g., or other functionality provided by othersoftware/hardware of the device 102), at which point access client 100can complete the process to log a user onto a network, as described inconnection with one or more embodiments of the present disclosure. Forexample, once O/S 158 establishes a connection, disclosed embodimentsprovide the ability to obtain information corresponding to the networkinterface connection established by the network driver/interface 152,such as the SSID (for Wi-Fi) of the network. The obtained informationcan then be used to retrieve information about the network from APdatabase 168 (also referred to as AP database 116) in U.S. patentapplication Ser. No. 10/325,450.

In accordance with one or more embodiments, rather than displaying alist of networks/signals detected such that the user can select one, O/S158 can be used to select a network (e.g., using Wireless ZeroConfiguration Service (WZC) provided by Windows XP). Since O/S 158 isused to select a network, in accordance with one or more embodiments,user preference, profile or network list storing need not be used. OnceO/S 158 (or other component(s)) select the network, client 167 canselect an account for the user to connect to wireless network 102, andthen log the user onto the wireless network 102 using authenticationinformation associated with the selected account.

In accordance with embodiments disclosed, sniffer logic 200 andassociation logic 204 need not be used, since client 167 functions tomonitor network interface connections to determine whether a networkinterface connection becomes available and is connected, and to initiatea login process such as that described in U.S. patent application Ser.No. 10/325,450. In accordance with one or more embodiments disclosedherein, however, client 167 can use the updater logic 212, login logic206 and databases (e.g., databases 116 to 118 and 120 on the client ofU.S. patent application Ser. No. 10/325,450.

One or more embodiments disclosed herein can use an authenticationsequence, such as that shown in FIG. 12 (e.g., elements 1308, 1310,1312, 1314, 1316, 1318 and 1320) of U.S. patent application Ser. No.10/325,450 to authenticate a user, for example.

In accordance with one or more embodiments, behavior/appearance of anaccess point icon such as that described U.S. patent application Ser.No. 10/325,450, can be modified to reflect three states of client 167.Such an access point icon can appear white when client 167 detects aconnection to a known AP 112 but the login process has not yet beencompleted, and no access point icon in a case that there is noconnection to a known AP 112 is detected or there is a detectedconnection to an unknown AP 112. Transition from the white state togreen occurs by operation of a login process, and a transition fromgreen to white can occur by operation of a logout process. Transitionfrom no icon to a white state can occur by way of establishing aconnection to a known network (e.g., via O/S 158), and transition from awhite or green icon to no icon can occur by way of a disconnection fromthe network (e.g., by something other than client 167).

In accordance with one or more embodiments, client 167 can be used tocollect quality of service data and can be updated, such as thatdescribed in U.S. patent application Ser. No. 10/325,450 (e.g.,including that depicted in FIGS. 9 to 11 and related discussion). Inaddition and in accordance with embodiments disclosed, client 167 can beconfigured to use method scripts described in U.S. patent applicationSer. No. 10/325,450 (e.g., including the description relating to FIGS.16 to 18 of U.S. patent application Ser. No. 10/325,450).

Similarly, embodiments of the present disclosure can be used to augment,supplement, or modify, functionality provided by client 108 of U.S.patent application Ser. No. 11/435,019. As described herein client 167can be used to passively detect an available network connection, whichavailable network connection can then be used to log a user onto awireless network 102. Embodiments disclosed herein can use the scriptingcapabilities described in U.S. patent application Ser. No. 11/435,019.

In accordance with one or more embodiments, client 167 can use suchconfiguration format such as that shown and described in either of U.S.patent application Ser. Nos. 10/325,450 and 11/435,019.

The above are not intended to be examples a manner in which featuresdescribed in one or both of U.S. patent application Ser. Nos. 10/325,450and 11/435,019 can be used in accordance with one or more embodiments ofdisclosed herein. It should be apparent that this is not an exhaustiveset. For example, and with limitation, various other aspects of thescripting and configuration file format described in U.S. patentapplication Ser. No. 11/435,019 can be used with one or more embodimentsof the present disclosure.

While the apparatus and method have been described in terms of what arepresently considered to be the most practical and preferred embodiments,it is to be understood that the disclosure need not be limited to thedisclosed embodiments. It is intended to cover various modifications andsimilar arrangements included within the spirit and scope of the claims,the scope of which should be accorded the broadest interpretation so asto encompass all such modifications and similar structures. The presentdisclosure includes any and all embodiments of the following claims.

1. A method for execution on a client device of achieving login to awireless network, the method comprising: employing a first softwarecomponent stored on the client device to establish a first connectionwith a wireless network; employing a client utility on the client deviceto identify that the first software component on the client device hasestablished the first connection with the wireless network; andperforming in the client utility on the client device, in response tothe identified first connection, a login procedure for authenticatingthe client device, the login procedure enabling the client device to usethe wireless network, wherein the login procedure is performed by theclient utility after the first software component has established thefirst connection with the wireless network, wherein the login procedureincludes establishing a high-level connection with the wireless network.2. The method of claim 1, wherein the first connection is an initiallow-level connection to the wireless network.
 3. The method of claim 1,wherein the first software component is an operating system running onthe client device.
 4. The method of claim 1, wherein the first softwarecomponent includes one or more network interface components operating onthe client device, the method further comprising: identifying one ormore network interface components operating on the client device;monitoring activity of said identified network interface components, andperforming the following in response to the identified networkconnection: obtaining a network identifier associated with the detectednetwork connection; determining, using the obtained network identifier,whether the detected network connection corresponds to a known network;and performing the login procedure to authenticate the client device forthe wireless network in a case that the obtained network identifiercorresponds to a known network.
 5. The method of claim 4, furthercomprising: determining whether multiple accounts are available for usein establishing a network session for a user; identifying a selected oneof the multiple accounts in a case that multiple accounts are determinedto be available; and retrieving a login procedure corresponding to theselected account for use in establishing a network session for the user.6. The method of claim 5, wherein identifying a selected one of themultiple accounts further comprises: notifying the user that theselected one of the multiple accounts is available to the user, so as toallow the user to identify the selected one of the multiple accounts. 7.The method of claim 5, wherein the selected one of the multiple accountsis provided by a wireless provider which acts as an interface betweenthe user and one or more other wireless providers.
 8. The method ofclaim 4, wherein the network identifier comprises a SSID.
 9. The methodof claim 4, further comprising determining, using the obtained networkidentifier, whether the detected network connection corresponds to aknown network by querying a database to determine whether the obtainednetwork identifier is contained in the database.
 10. The method of claim9, wherein the database further comprises the login procedure and saidstep of retrieving the login procedure further comprises retrieving thelogin procedure from the database.
 11. The method of claim 4, whereinsaid monitoring step is performed periodically and even in a case that anetwork connection is detected.
 12. The method of claim 4, furthercomprising: notifying the user of the network session.
 13. The method ofclaim 12, wherein said step of notifying uses a displayed icon, thedisplayed icon changing appearance in response to said network sessionbeing established.
 14. The method of claim 12, wherein said step ofnotifying uses a dialog window displaying a notification in response tosaid network session being established.
 15. The method of claim 12,wherein said step of notifying uses a displayed icon and a dialogwindow, the displayed icon changing appearance and the dialog windowdisplaying a notification in response to said network session beingestablished.
 16. The method of claim 1, further comprising: determiningwhether the wireless network requires probing; performing the loginprocedure if no probing is required; and if probing is required,performing the following: probing the network, and determining whetherthe probing of the network was successful, and if successful, performingthe login procedure.
 17. The method of claim 16, further comprising:determining whether results from a prior probing of the network exist;and utilizing the prior probing results instead of performing theprobing of the network.
 18. The method of claim 16, wherein the probingstep comprises: detecting a beacon message from at least one accesspoint of the wireless network, the beacon message including informationidentifying the access point; attempting, using at least one predefinedoperation, to communicate with the access point; determining a usabilitystatus based on a response received from the access point to the atleast one predefined operation; and storing the determined usabilitystatus in a cache, the usability status being associated with a uniqueidentifier of the access point.
 19. The method of claim 1, in responseto the identified network connection, further comprising: determiningwhether a user of the client device is already subscribed for service ofthe wireless network; performing the login procedure if the user of theclient device is already subscribed to the wireless network; and if notalready subscribed, prompting the user of the client device with theopportunity to become subscribed to the wireless network.
 20. Anon-transitory machine-readable storage medium having persistent programinstructions tangibly stored thereon executable by a processing unit ona client device for achieving login to a wireless network by performingthe steps of: employing a first component on the client device toestablish an initial connection with a wireless network; employing aclient utility on the client device to identify that the first softwarecomponent on the client device has established a connection with awireless network; performing in the client utility on the client device,in response to the identified network connection, a login procedure forauthenticating the client device for enabling use of the wirelessnetwork, wherein the login procedure is performed by the client utilityafter the first software component has established the initialconnection to the wireless network and wherein the login procedureperformed by the client utility is wholly separate from the connectionestablished by the first software component to the wireless network. 21.A device capable of achieving login to a wireless network, comprising:an operating system capable of establishing a low-level connection witha wireless network; and a client utility, which, in response todetecting an established low level connection, is capable of performinga login procedure for authenticating the device, the login procedureenabling the device to use the wireless network, wherein the loginprocedure is performed by the client utility after the low levelconnection to the wireless network is established by the operatingsystem.
 22. The method of claim 1, further comprising: identifying thata Layer 2 or Layer 3 connection has been established by the firstsoftware component on the client device; and in response to andindependent from the identified Layer 2 or Layer 3 connection,authenticating the client device for use of the wireless network byperforming the login procedure in the client utility at a higher levelthan the identified Layer 2 or Layer 3 connection.
 23. A method forexecution on a client device of achieving login to a wireless network,the method comprising: conducting active scanning for a wireless networkunder control of a first software component on the client device andestablishing a connection with the wireless network using that softwarecomponent; detecting that the first software component on the clientdevice has established a connection with the wireless network; andresponding to detection of the establishment of a connection with thewireless network by the software component by employing a client utilityto perform a login procedure for authenticating the client device, saidauthenticating of the client device being required to enable a user touse the wireless network, wherein the login procedure includesestablishing a high-level connection to the wireless network.
 24. Themethod of claim 23, wherein the client utility does not perform activescanning or participate in establishment of the connection with thewireless network.
 25. The method of claim 23, wherein the client utilityis inactive until detection of establishment of a connection with thewireless network.
 26. The method of claim 23, wherein the client utilityis stored on the client device.
 27. The method of claim 23, wherein theconnection with the wireless network comprises a low-level connection.28. The method of claim 23, wherein the first software componentcomprises an operating system running on the client device.
 29. A methodfor execution on a client device of achieving login to a wirelessnetwork, the method comprising: identifying that a first softwarecomponent on the client device has established a connection with awireless network; and performing in a client utility on the clientdevice, in response to the identified network connection, a loginprocedure for authenticating the client device to thereby enable theclient device and its user to use the wireless network, wherein thelogin procedure performed by the client utility is performed whollyseparately and apart from a procedure implemented previously by thefirst component to establish the connection to the wireless network,wherein the login procedure includes establishing a high-levelconnection to the wireless network.
 30. The method of claim 29, whereinthe first software component comprises an operating system running onthe client device.
 31. A method for execution on a client device ofachieving login to a wireless network, the method comprising: employinga first software component stored on the client device to establish aninitial connection with a wireless network; employing a client utilityon the client device to identify that the first software component onthe client device has established a connection with the wirelessnetwork; performing in the client utility on the client device, inresponse to the identified network connection, a login procedure forauthenticating the client device, the login procedure enabling theclient device to use the wireless network, wherein the login procedureis performed by the client utility after the first software componenthas established the initial connection to the wireless network
 32. Adevice capable of achieving login to a wireless network, comprising:means for employing a first software component stored on the device toestablish an initial connection with a wireless network; means foridentifying that the first software component on the device hasestablished a connection with a wireless network; and means forperforming in response to the identified network connection, a loginprocedure for authenticating the device, the login procedure enablingthe device to use the wireless network, wherein the login procedure isperformed by a client utility after the first software component hasestablished the initial connection to the wireless network.
 33. Themethod of claim 1 wherein the first software component is an operatingsystem which initially establishes a low level connection with thewireless network and wherein the client utility monitors the status ofone or more network drivers to detect that the operating system hasestablished the initial low level connection with the wireless networkand responds to such detection by executing the login procedure.